home *** CD-ROM | disk | FTP | other *** search
-
-
-
- PPPPMMMMEEEEMMMM((((1111)))) PPPPMMMMEEEEMMMM((((1111))))
-
-
-
- NNNNAAAAMMMMEEEE
- ppppmmmmeeeemmmm - report per-process memory usage
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- ppppmmmmeeeemmmm [----aaaa _a_r_c_h_i_v_e] [----hhhh _h_o_s_t] [----nnnn _p_m_n_s_f_i_l_e] [----SSSS _s_t_a_r_t_t_i_m_e] [----uuuu _u_s_e_r_n_a_m_e]
- [----wwww] [----zzzz] [----ZZZZ _t_i_m_e_z_o_n_e]
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- ppppmmmmeeeemmmm reports per-process memory usage statistics within the Performance
- Co-Pilot framework. Both virtual size and pro-rated physical memory
- usage are reported.
-
- Unless directed to another host by the ----hhhh option, ppppmmmmeeeemmmm will contact the
- PMCD (see ppppmmmmccccdddd(1)) on the local host to obtain the required information.
- Alternatively, the ----aaaa option may be used to obtain the required
- information from an archive (see ppppmmmmllllooooggggggggeeeerrrr(1)). If the ----aaaa option is used,
- then the ----SSSS option may be used to specify the temporal position relative
- to the start of the archive in seconds.
-
- The ----uuuu option restricts the report to the specified _u_s_e_r_n_a_m_e on the
- target host or archive. Normally the report is truncated at the 80th
- column. This is over-ridden with the ----wwww option.
-
- By default, ppppmmmmeeeemmmm reports the time of day according to the local timezone
- on the system where ppppmmmmeeeemmmm is run. The ----ZZZZ option changes the timezone to
- _t_i_m_e_z_o_n_e in the format of the environment variable TTTTZZZZ as described in
- eeeennnnvvvviiiirrrroooonnnn(5). The ----zzzz option changes the timezone to the local timezone at
- the host that is the source of the performance metrics, as identified via
- either the ----hhhh or ----aaaa options.
-
- Normally ppppmmmmeeeemmmm operates on the default Performance Metrics Namespace
- (PMNS), however if the ----nnnn option is specified an alternative namespace is
- loaded from the file _p_m_n_s_f_i_l_e.
-
- If the PCP product is installed, then the tools ppppssssmmmmoooonnnn(1) and
- mmmmkkkkppppmmmmeeeemmmmaaaarrrrcccchhhh(1) are available to assist in the creation of PCP archives
- that can be replayed with ppppmmmmeeeemmmm(1).
-
- RRRREEEEPPPPOOOORRRRTTTT FFFFOOOORRRRMMMMAAAATTTT
- In the report, all sizes are reported in Kbytes unless shown with a
- suffix of MMMM, in which case the size is Mbytes (multiples of 1048576
- bytes), or a suffix of GGGG, in which case the size is Gbytes (multiples of
- 1073741824 bytes). The virtual memory usage statistics represent the
- total virtual size of each process, irrespective of how many pages are
- valid (resident). The physical memory statistics indicate real memory
- usage (only valid pages are counted) and are pro-rated on a per-page
- basis between all processes which reference each page.
-
- The columns in the report should be interpreted as follows:
-
-
-
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- PPPPMMMMEEEEMMMM((((1111)))) PPPPMMMMEEEEMMMM((((1111))))
-
-
-
- ppppiiiidddd Process ID.
-
- ppppppppiiiidddd Parent process ID.
-
- uuuusssseeeerrrrnnnnaaaammmmeeee User name of process owner.
-
- vvvvttttxxxxtttt Total virtual memory used by text (executable code) regions
- mapped by the process.
-
- ppppttttxxxxtttt Pro-rated physical memory used by text regions.
-
- vvvvddddaaaatttt Total virtual memory used by all non-executable regions,
- excluding shared memory regions. This includes initialized
- data, bss and stack but not shared memory regions.
-
- ppppddddaaaatttt Pro-rated physical memory used by all data regions (data, bss
- and stack but not shared memory regions).
-
- vvvvsssshhhhmmmm Total virtual memory used by all shared memory regions.
-
- ppppsssshhhhmmmm Pro-rated physical memory used by shared memory regions.
-
- ccccoooommmmmmmmaaaannnndddd The command and arguments, truncated so each line in the report
- is at most 80 columns (unless the ----wwww option is given).
-
- The report heading shows the amount of physical memory configured on the
- target host and the amount of free memory, as reported by the operating
- system (see the PCP metric mmmmeeeemmmm....ffffrrrreeeeeeeemmmmeeeemmmm).
-
- Only memory used in user space is counted - memory used in kernel tables
- such as that used for pppptttteeees (page table entries), and the pppprrrroooocccc and uuuusssseeeerrrr
- structures are not counted because they are allocated in the kernel's
- address space.
-
- If any shared memory segments are found with no process attachment, the
- size of these are summed. If the total is more than 4096 bytes, then
- this is reported as vvvvsssshhhhmmmm belonging to a virtual process with a ccccoooommmmmmmmaaaannnndddd of
- ``orphaned shmem'' and a ppppiiiidddd of ``???''.
-
- At the end of the report, a summary is printed indicating the totals for
- each column and the grand totals. The difference between the total
- physical memory in use by all processes and the total configured physical
- memory will always be more than the free memory reported by the operating
- system because the latter also accounts for memory allocated in the
- kernels address space.
-
- All statistics are accurate to within one 256th of a page.
-
- FFFFIIIILLLLEEEESSSS
- $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ppppmmmmnnnnssss////*
- default PMNS specification files
-
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-
-
-
- PPPPMMMMEEEEMMMM((((1111)))) PPPPMMMMEEEEMMMM((((1111))))
-
-
-
- PPPPCCCCPPPP EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT
- Environment variables with the prefix PPPPCCCCPPPP____ are used to parameterize the
- file and directory names used by PCP. On each installation, the file
- /_e_t_c/_p_c_p._c_o_n_f contains the local values for these variables. The
- $$$$PPPPCCCCPPPP____CCCCOOOONNNNFFFF variable may be used to specify an alternative configuration
- file, as described in ppppccccpppp....ccccoooonnnnffff(4).
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- mmmmkkkkppppmmmmeeeemmmmaaaarrrrcccchhhh(1), ppppmmmmccccdddd(1), ppppmmmmcccchhhhaaaarrrrtttt(1), ppppmmmmdddduuuummmmpppplllloooogggg(1), ppppmmmmiiiinnnnffffoooo(1), ppppmmmmllllooooggggggggeeeerrrr(1),
- ppppmmmmvvvvaaaallll(1) and sssspppprrrroooocccc(2).
-
- DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
- All are generated on standard error and are intended to be self-
- explanatory.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 3333
-
-
-
-